docs: add single-host monitoring guide for Arc EL + CL#47
Open
Bela1401 wants to merge 5 commits intocirclefin:mainfrom
Open
docs: add single-host monitoring guide for Arc EL + CL#47Bela1401 wants to merge 5 commits intocirclefin:mainfrom
Bela1401 wants to merge 5 commits intocirclefin:mainfrom
Conversation
Add Prometheus and Grafana setup instructions for a single Arc EL + CL node on one host.
Add a reference to docs/monitoring.md from running-an-arc-node.md.
Author
|
Reopened this as a fresh PR on top of the updated This supersedes #28. |
Author
Validation screenshots from the earlier single-host setup are attached below for context.
|
sdaveas-circle
left a comment
sdaveas-circle
left a comment
There was a problem hiding this comment.
I tested the guide's configs against a running EL+CL network (Quake testnet with 5 validators). The technical content is solid:
- Prometheus scrapes both EL (
/) and CL (/metrics) successfully - Grafana auto-provisions 8 dashboards from the repo's existing JSONs
- Datasource UID
prometheusresolves correctly - Real metrics data flows end-to-end (verified
reth_info,arc_malachite_app_block_time_count, both targetsup)
The configs, ports, paths, and network_mode: host approach all work correctly. One critical formatting issue blocks merging — see inline comment.
Add missing code fences (```sh/```yaml) around all shell commands and config blocks. Promote plain-text section titles to proper ## and ### headings. Format inline paths, URLs, and lists as markdown. No content changes.
|
@Bela1401 I opened a PR to suggest some clearer formatting for sections and code blocks. Please take a look when you have the chance! |
docs: fix markdown fences and heading structure
Author
|
Merged the suggested formatting updates from the follow-up PR in my fork. Thanks. |
ZhiyuCircle
approved these changes
Apr 27, 2026
sdaveas-circle
approved these changes
Apr 27, 2026
ZhiyuCircle
added
pending-import
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds a practical monitoring guide for operators running a single Arc
execution layer + consensus layer on one Ubuntu host.
It documents:
Scope
This PR intentionally stays focused on a single-host operator setup and does not
attempt to cover multi-node or production observability architectures.
Related docs change
This PR also adds a reference from
docs/running-an-arc-node.mdto the newdocs/monitoring.mdguide.Notes
This PR supersedes the earlier closed PR #28, which was auto-closed after the
target branch changed.